Skip to content

Move annotations channel changelog entries to 0.4.0#262

Merged
connor4312 merged 1 commit into
mainfrom
fix-issue-222
Jun 24, 2026
Merged

Move annotations channel changelog entries to 0.4.0#262
connor4312 merged 1 commit into
mainfrom
fix-issue-222

Conversation

@connor4312

Copy link
Copy Markdown
Member

Summary

Fixes #222.

The annotations channel was documented under ## [0.3.0] in all six CHANGELOGs (root + Rust/Kotlin/Swift/TypeScript/Go) and mapped to '0.3.0' in types/version/registry.ts, but it never shipped in spec/v0.3.0. The types/channels-annotations/ sources first appear at the spec/v0.4.0 tag (where PROTOCOL_VERSION is 0.4.0), so the channel actually shipped in 0.4.0. (annotations/updated was already correctly attributed to 0.4.0.)

Changes

  • All six CHANGELOGs: moved the annotations-channel bullets (AnnotationsState / Annotation / AnnotationEntry / AnnotationsSummary, the annotations/set|removed|entrySet|entryRemoved actions, MessageAnnotationsAttachment, SessionSummary.annotations, reducer/snapshot slots) from [0.3.0][0.4.0].
  • types/version/registry.ts: corrected ACTION_INTRODUCED_IN for AnnotationsSet/Removed/EntrySet/EntryRemoved from '0.3.0''0.4.0', so isActionKnownToVersion no longer reports annotations as available to peers negotiating 0.3.0.
  • Added ### Fixed entries under [Unreleased] in the root and TypeScript changelogs for the registry correction. The introduced-in map is TypeScript-only (not mirrored into the other clients), confirmed by npm run generate producing zero generated diffs.

Verification

  • npm run generate → no generated-file changes.
  • npm run test → 267 passed, 0 failed (typecheck, eslint, verify:release-metadata, verify:changelog, 100% reducer branch coverage).

The annotations channel (state types, `annotations/set|removed|entrySet|
entryRemoved` actions, `MessageAnnotationsAttachment`,
`SessionSummary.annotations`) was documented under `## [0.3.0]` in every
CHANGELOG and mapped to `'0.3.0'` in `ACTION_INTRODUCED_IN`, but it never
shipped in `spec/v0.3.0`. Its sources first appear at the `spec/v0.4.0` tag,
so the channel actually shipped in 0.4.0.

Move the annotations bullets from `[0.3.0]` to `[0.4.0]` across all six
changelogs and correct the registry's introduced-in versions to `0.4.0`, so
`isActionKnownToVersion` no longer advertises annotations to peers negotiating
`0.3.0`.

Fixes #222

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@connor4312 connor4312 enabled auto-merge (squash) June 24, 2026 22:31
@connor4312 connor4312 merged commit 975f041 into main Jun 24, 2026
8 checks passed
@connor4312 connor4312 deleted the fix-issue-222 branch June 24, 2026 23:19
yucm002-ops pushed a commit to yucm002-ops/agent-host-protocol that referenced this pull request Jun 25, 2026
The annotations channel (state types, `annotations/set|removed|entrySet|
entryRemoved` actions, `MessageAnnotationsAttachment`,
`SessionSummary.annotations`) was documented under `## [0.3.0]` in every
CHANGELOG and mapped to `'0.3.0'` in `ACTION_INTRODUCED_IN`, but it never
shipped in `spec/v0.3.0`. Its sources first appear at the `spec/v0.4.0` tag,
so the channel actually shipped in 0.4.0.

Move the annotations bullets from `[0.3.0]` to `[0.4.0]` across all six
changelogs and correct the registry's introduced-in versions to `0.4.0`, so
`isActionKnownToVersion` no longer advertises annotations to peers negotiating
`0.3.0`.

Fixes microsoft#222

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CHANGELOG documents the annotations channel under [0.3.0], but it isn't in the spec/v0.3.0 release (or any client tag)

2 participants